Here's a summary of the many ways to package a jar with idea, and later package packages can refer to the following form:
The package form with idea comes in
Package with Maven plugin maven-shade-plugin
Package with Maven
Add the following code under the Pom.xml File build node:123 45678 9Ten One A - -The user can bind any plug-in target to the stage of any life cycle as needed, such as binding the jar-no-fork target of Maven-source-plugin to the package stage of the default life cycle, so that later execution mvn Package command when packaging a project, source code packaging is performed after the
Failed to execute goal on Project: cocould not resolve dependencies for project cs2c. nkscloudweb: nkscloudweb3: War: 3.0: The following artifacts cocould not be resolved:Maven-plugins: Maven-cobertura-plugin: Plugin: 1.3, Maven-plugins: Maven-findbugs-
The Spring boot maven plugin (Spring boot maven plugin) provides spring boot support for applications in Maven, which provides the possibility for the spring boot application to perform MAVEN operations.Spring Boot
Requirements:
When Maven compiles a project, the amount of statistical code, that is, the number of files in the project, the number of lines of code, including Java files and configuration files Two, where the configuration file (SQL, XML, properties) code lines/4 processing.
To Create a project:
First make sure that the M2eclipse plugin is installed: http://eclipse.org/m2e/
Eclipse-new-
elasticsearch.yml file in the config file in the Elasticsearch-analysis-ik-master directory is then overwritten with the elasticsearch.yml file in the Config directory elasticsearch the installation directory.3, into the extracted folder directory, because the source code needs to use the MAVEN command package, execute the following command:MVN Clean PackageIf y
maven dependencies in the Pom file in the Java projectElasticsearch-releasesHttps://maven.elasticsearch.org/releasesTrueFalse
Org.elasticsearch.pluginShield2.4.3Note: The Maven dependent version of Shield must be 2.4.3, and the official example is that 2.2.0 is not working properly. Because our shield installed version is also 2.4.3, to keep the version consistent.
2: The code is as follows:Settings Settin
Common commandsTomcat7:deployDescription: Deploy WAR to TomcatTomcat7:helpDescription: View plug-in Help informationTomcat7:runDescription: Sub-branch current projectConfigurationProject> ... Build> To define the plugin version in your parent POM - pluginmanagement> Plugins> plugin> groupId>Org.apache.tomcat.mavengroupId> Artifactid>Tomcat7-
Long time no blog, recently worked overtime to do the project, is doing search work, so tested ES, after countless failures, and finally successfully installed the Es+ikFrom the Internet to find countless installation methods are the same, the installation is unsuccessfulES 2.0 InstallationES official website Download es2, after decompression can be executed, can be temporarily not configured, I only modified the data and log pathDownload IK https://github.com/medcl/
In the project release, you may encounter this situation, I hope that the project source code to maintain the same premise, you want to be able to target different operating environment to obtain the corresponding running package. (e.g. War pack)Basic Configuration : (including the configuration of the jar that does not want to enter the war package ) Reference: http://nileader.blog.51cto.com/1381108/449956Maven-war-plugin Official website: http://m
Excerpt from: http://www.mayou18.com/detail/nTxPQSyu.html "ElasticSearch Foundation" elasticsearch+spring Integrated maven dependenciesMaven DependencySpring-data-elasticsearch and Elasticsearch version correspondence table
Spring Data
The maven dependency of the Maven-jar-plugin plugin is:One: Package runnable jarConfigured to:Assuming that the project has dependencies on other jars, it is necessary for the Maven-dependency-plugin
The maven dependency of the Maven-jar-plugin plugin is:One: Package the executable jarConfigured to:If the project has dependencies on other jars, the Maven-dependency-plugin plug-in will need to be packaged with other dependencie
/*** System Environment: CentOS 7.2 under VM12* Current installation version: Elasticsearch-2.4.0.tar.gz*/Installation and learning can be referred to the official documentation:1, installation-l-o https://download.elastic.co/elasticsearch/release/org/elasticsearch/distribution/tar/ elasticsearch/2.4.0/
1. In the Pom.xml file, introduce the Wro4j-maven-plugin plugin
ro.isdc.wro4j
wro4j-maven-plugin
${wro4j.version}
optimize-web-resources
compile
Run
false
${project.build.directory}/${project.build.finalname}/s
The pom.xml dependency of the Tomcat7-maven-plugin plugin is:One: Run the WebApp project directlyExecute MVN Tomcat7:runAccess Http://127.0.0.1:9090/taobaoII: Deploy the project to TomcatFirst, configure the Conf/tomcat-users.xml file inside theTwo methods of deployment(1)Configure the plugin directly inside the Pom.xm
Maven project-fixed Plugin execution not covered by lifecycle configuration: org. codehaus. mojo: build-helper-maven-plugin: 1.8: add-resource (execution: add-resource, phase: generate-resources) pom. xml error,
1: pom. xml Code
2: the error message is as follows:
Plugin
Elasticsearch is a very useful search engine, it is the bottom of the integration of luence, so also inherited the inverted indexing principle. To use elasticsearch here we need a few tools and follow these steps.
This project is just as a basic introductory demo Elasticsearch simple function reference, the actual deployment of multiple nodes and the idea of deal
1: Configure the Tomcat Manager User: Re-unzipped a new TOMCAT7, open Tomcat_user.xml in the Conf directory under the Tomcat root directory, add Manager roles and users under Adding Tomcat Server to the 2:maven configuration Open maven's settings.xml file, if it is a locally installed version of MAVEN, the file is installed in the root directory conf/settings.xml, if you are using the eclipse built-in
The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion;
products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the
content of the page makes you feel confusing, please write us an email, we will handle the problem
within 5 days after receiving your email.
If you find any instances of plagiarism from the community, please send an email to:
info-contact@alibabacloud.com
and provide relevant evidence. A staff member will contact you within 5 working days.